Documentation revamp. #4129
Merged
Documentation revamp. #4129
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PR HealthChangelog Entry ✔️
Changes to files need to be accounted for in their respective changelogs. |
davidmorgan
force-pushed
the
documentation
branch
6 times, most recently
from
c4afc35 to
41930e4
Compare
davidmorgan
force-pushed
the
documentation
branch
from
41930e4 to
a6eeed2
Compare
jensjoha
approved these changes
Aug 12, 2025
Thanks! I added a column listing endorsements and a note that we don't endorse if not mentioned, how does that look to you please? |
jensjoha
reviewed
Aug 13, 2025
q0w
added a commit
to q0w/site-www
that referenced
this pull request
Sep 3, 2025
This pages are gone due to dart-lang/build#4129
4 tasks
antfitch
added a commit
to dart-lang/site-www
that referenced
this pull request
Sep 4, 2025
These pages are gone due to dart-lang/build#4129 Preview: https://dart-dev--pr6837-patch-1-8lua4imh.web.app/tools/build_runner --- - [x] I’ve reviewed the contributor guide and applied the relevant portions to this PR. - [x] This PR doesn't contain automatically generated corrections or text (Grammarly, LLMs, and similar). - [x] This PR follows the [Google Developer Documentation Style Guidelines](https://developers.google.com/style) — for example, it doesn't use _i.e._ or _e.g._, and it avoids _I_ and _we_ (first person). - [x] This PR uses [semantic line breaks](https://github.com/dart-lang/site-shared/blob/main/doc/writing-for-dart-and-flutter-websites.md#semantic-line-breaks) of 80 characters or fewer. <details> <summary>Contribution guidelines:</summary><br> - See our [contributor guide](https://github.com/dart-lang/site-www/blob/main/CONTRIBUTING.md) for general expectations for PRs. - Larger or significant changes should be discussed in an issue before creating a PR. - Code changes should generally follow the [Dart style guide](https://dart.dev/effective-dart) and use `dart format`. - Updates to [code excerpts](https://github.com/dart-lang/site-shared/blob/main/packages/excerpter) indicated by `<?code-excerpt` need to be updated in their source `.dart` file as well. </details> --------- Co-authored-by: Amanda Fitch <[email protected]>
connie-ooi
pushed a commit
to connie-ooi/site-www
that referenced
this pull request
Sep 4, 2025
These pages are gone due to dart-lang/build#4129 Preview: https://dart-dev--pr6837-patch-1-8lua4imh.web.app/tools/build_runner --- - [x] I’ve reviewed the contributor guide and applied the relevant portions to this PR. - [x] This PR doesn't contain automatically generated corrections or text (Grammarly, LLMs, and similar). - [x] This PR follows the [Google Developer Documentation Style Guidelines](https://developers.google.com/style) — for example, it doesn't use _i.e._ or _e.g._, and it avoids _I_ and _we_ (first person). - [x] This PR uses [semantic line breaks](https://github.com/dart-lang/site-shared/blob/main/doc/writing-for-dart-and-flutter-websites.md#semantic-line-breaks) of 80 characters or fewer. <details> <summary>Contribution guidelines:</summary><br> - See our [contributor guide](https://github.com/dart-lang/site-www/blob/main/CONTRIBUTING.md) for general expectations for PRs. - Larger or significant changes should be discussed in an issue before creating a PR. - Code changes should generally follow the [Dart style guide](https://dart.dev/effective-dart) and use `dart format`. - Updates to [code excerpts](https://github.com/dart-lang/site-shared/blob/main/packages/excerpter) indicated by `<?code-excerpt` need to be updated in their source `.dart` file as well. </details> --------- Co-authored-by: Amanda Fitch <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For #4119.
Full rewrite of the most obviously user-facing docs with a focus on how people mostly use build_runner today: build_runner, build, build_test. Added a list of popular builders based mostly on download stats from pub.dev.
Tweaks/cleanup but not a rewrite of docs that are not so user-facing: build_config, build_web_compilers.
Removed most other docs and FAQs, a lot of it is out of date and refers to niche uses of build_runner. Moved a few FAQ entries related to build_config into the build_config doc.